cc @EricJizbaMSFT

verrfied debugger breaks into a js function with runonstartup set to true for the first invocation with following tasks.json

{
  "version": "2.0.0",
  "tasks": [
    {
      "type": "func",
      "command": "host start",
      "isBackground": true,
      "dependsOn": "npm install",
       "problemMatcher": {
        "base": "$func-watch",
        "background": {
          "activeOnStart": true,
          "beginsPattern": "^.*(Job host stopped|signaling restart).*$",
          "endsPattern": "^.*Worker process started and initialized.*$"
        },
       }
    },
    {
      "type": "shell",
      "label": "npm install",
      "command": "npm install"
    },
    {
      "type": "shell",
      "label": "npm prune",
      "command": "npm prune --production",
      "problemMatcher": []
    }
  ]
}

We're currently getting bit by this bug #4384 in production. We have a python http trigger on consumption plan intermittently failing with: Did not find any initialized language workers

"Anxiously awaiting this fix! 💪 Status? Where can I track if our our Azure environment gets the latest bits?"
Nevermind, found it. Application Insights (Kusto) has got the sdkversion column which correlate to the release tags.
I can confirm that we are only seeing this error on older versions, such as 3.0.13901.0 Runs on the latest version are healthy.
Thanks all.